Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 98cda4d5378e171732ce72d425b1dc95ec4c480d64901255f99e308e77fa57d3

Tx prefix hash: ab49c4eaab93c9175d632969648ea751bfb0fef45c2c6e37088fa995b765e348
Tx public key: 92ff2478df49cb5b45066a2755275881d88acb6ab6f5c8da05086834c8b89409
Timestamp: 1723762895 Timestamp [UTC]: 2024-08-15 23:01:35 Age [y:d:h:m:s]: 02:091:17:01:26
Block: 1088756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590252 RingCT/type: yes/0
Extra: 0192ff2478df49cb5b45066a2755275881d88acb6ab6f5c8da05086834c8b89409021100000004e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b63cecef1313d3cfe5d7b2d5a10537ab01bf400bd995d67e9a2554d44f2c9531 0.000600000000 1563375 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1088766, "vin": [ { "gen": { "height": 1088756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b63cecef1313d3cfe5d7b2d5a10537ab01bf400bd995d67e9a2554d44f2c9531" } } ], "extra": [ 1, 146, 255, 36, 120, 223, 73, 203, 91, 69, 6, 106, 39, 85, 39, 88, 129, 216, 138, 203, 106, 182, 245, 200, 218, 5, 8, 104, 52, 200, 184, 148, 9, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: