Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c853eab5dd3e7ff175637f5cd4c078c95822c38868f29354ccb944dda4b383d0

Tx prefix hash: 2571b824b2bbf455fab17dafdc17f65f16800afe845d4ee2c8774cab4259bbb2
Tx public key: 6c94d4be6afe592a36df1472f04dfc9ab9e3cf9af3aab1622250a075a358cc9d
Timestamp: 1737745683 Timestamp [UCT]: 2025-01-24 19:08:03 Age [y:d:h:m:s]: 00:331:06:29:02
Block: 1204476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234356 RingCT/type: yes/0
Extra: 016c94d4be6afe592a36df1472f04dfc9ab9e3cf9af3aab1622250a075a358cc9d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e6514985d8b5341dc579bbc571a80b8afa4d245b9b72e0a9866218084beab17 0.600000000000 1691163 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": 1204486, "vin": [ { "gen": { "height": 1204476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e6514985d8b5341dc579bbc571a80b8afa4d245b9b72e0a9866218084beab17" } } ], "extra": [ 1, 108, 148, 212, 190, 106, 254, 89, 42, 54, 223, 20, 114, 240, 77, 252, 154, 185, 227, 207, 154, 243, 170, 177, 98, 34, 80, 160, 117, 163, 88, 204, 157, 2, 17, 0, 0, 0, 4, 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