Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ced169c2d0cd98df5441b76894bfdeb5f088b58740aa5743321c0efeaaf44015

Tx prefix hash: 29dd1f2f7b24e13d4d9a7e0ad89ce7e529fbb678034a9fbd7a8a0007e9648b7a
Tx public key: 2672b04f6bf75ac803bde3d0b0a6a06f76dd4f48177de840816bd6a563f64d65
Timestamp: 1762607272 Timestamp [UCT]: 2025-11-08 13:07:52 Age [y:d:h:m:s]: 00:047:17:03:53
Block: 1407669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34154 RingCT/type: yes/0
Extra: 012672b04f6bf75ac803bde3d0b0a6a06f76dd4f48177de840816bd6a563f64d65021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dd067f44557c036f5e76f8778847dc108335790f32b9807b7abd0fa2031724f 0.600000000000 1896090 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": 1407679, "vin": [ { "gen": { "height": 1407669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dd067f44557c036f5e76f8778847dc108335790f32b9807b7abd0fa2031724f" } } ], "extra": [ 1, 38, 114, 176, 79, 107, 247, 90, 200, 3, 189, 227, 208, 176, 166, 160, 111, 118, 221, 79, 72, 23, 125, 232, 64, 129, 107, 214, 165, 99, 246, 77, 101, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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