Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bbc5a12e880ec0d5ea8136e3fd60904b874c978c182c3909cc6d0e61647b91d

Tx prefix hash: 1f80d3f25a00159c6b026332f0f5d6adefbd026c5df36842a4c285a2f42f0023
Tx public key: b9117b61aa9ebd1d871dde0890de0dcea055c59a7dcf6365031314c61de87dbc
Timestamp: 1738051439 Timestamp [UCT]: 2025-01-28 08:03:59 Age [y:d:h:m:s]: 00:293:05:11:40
Block: 1206803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207311 RingCT/type: yes/0
Extra: 01b9117b61aa9ebd1d871dde0890de0dcea055c59a7dcf6365031314c61de87dbc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89818ec4831b40bd511bcbe33ba1b5c67703f7992c5d2a9412d643fa85239006 0.600000000000 1693516 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": 1206813, "vin": [ { "gen": { "height": 1206803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89818ec4831b40bd511bcbe33ba1b5c67703f7992c5d2a9412d643fa85239006" } } ], "extra": [ 1, 185, 17, 123, 97, 170, 158, 189, 29, 135, 29, 222, 8, 144, 222, 13, 206, 160, 85, 197, 154, 125, 207, 99, 101, 3, 19, 20, 198, 29, 232, 125, 188, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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