Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf357ac60453bd511e9580fbd8e2fc7432f4c4a4b4d9f574ccb80c8643c3662

Tx prefix hash: 6cc98670005bd4fcae430d1b162f5d6f5b03d30d86b8ea610ce7c55557065c5d
Tx public key: 5584d1e7c3653730c76d4541e7ce64c61d035f07919519037cab4bd1d51f6ff7
Timestamp: 1755684926 Timestamp [UCT]: 2025-08-20 10:15:26 Age [y:d:h:m:s]: 00:090:12:59:11
Block: 1350510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64617 RingCT/type: yes/0
Extra: 015584d1e7c3653730c76d4541e7ce64c61d035f07919519037cab4bd1d51f6ff7021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06ccce27a02fac28a54c325d8099ff0fe95b12e8fe3035304cec4c0d096998e 0.600000000000 1838455 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 dinasty-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": 1350520, "vin": [ { "gen": { "height": 1350510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06ccce27a02fac28a54c325d8099ff0fe95b12e8fe3035304cec4c0d096998e" } } ], "extra": [ 1, 85, 132, 209, 231, 195, 101, 55, 48, 199, 109, 69, 65, 231, 206, 100, 198, 29, 3, 95, 7, 145, 149, 25, 3, 124, 171, 75, 209, 213, 31, 111, 247, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8