Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbe9e82cf086b039c7f0d096f1ab4bf51356f8b457efdff0d45d2b2936815a2f

Tx prefix hash: f22ddc03330c86dcb4173918b825ae3abc9264ee3d6da126590a5c9214398bc5
Tx public key: 66e6c1e9bb4b3d4df4972ebe73460c12873bdacf294dc644c85c3854aa9718dd
Timestamp: 1729507307 Timestamp [UCT]: 2024-10-21 10:41:47 Age [y:d:h:m:s]: 01:100:04:27:26
Block: 1136336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329930 RingCT/type: yes/0
Extra: 0166e6c1e9bb4b3d4df4972ebe73460c12873bdacf294dc644c85c3854aa9718dd021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b6144af29c411052dd16bb17560e97208292bc599a298dd7c8fadd2dbf57e2 0.600000000000 1619681 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": 1136346, "vin": [ { "gen": { "height": 1136336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b6144af29c411052dd16bb17560e97208292bc599a298dd7c8fadd2dbf57e2" } } ], "extra": [ 1, 102, 230, 193, 233, 187, 75, 61, 77, 244, 151, 46, 190, 115, 70, 12, 18, 135, 59, 218, 207, 41, 77, 198, 68, 200, 92, 56, 84, 170, 151, 24, 221, 2, 17, 0, 0, 0, 1, 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