Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cdb8d8516c0f4a31756d8556218d59fa63c1ba35802ead40a0ceeade46539ea

Tx prefix hash: fd0afde61d2cdf7ed7e0faff7a785079d9fd0bcb1b1f8f99ac253fb7fccab95e
Tx public key: 684043f4007fe2f8a23b2f4736533ee25f198afd4cbce974a1d5afa03859e067
Timestamp: 1748738429 Timestamp [UCT]: 2025-06-01 00:40:29 Age [y:d:h:m:s]: 00:170:22:31:05
Block: 1295276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119847 RingCT/type: yes/0
Extra: 01684043f4007fe2f8a23b2f4736533ee25f198afd4cbce974a1d5afa03859e06702110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 661af0878ce8bd4937c86c776fe71b8394b9d40fd74a96a4c486d33f3997753e 0.600000000000 1782779 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": 1295286, "vin": [ { "gen": { "height": 1295276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "661af0878ce8bd4937c86c776fe71b8394b9d40fd74a96a4c486d33f3997753e" } } ], "extra": [ 1, 104, 64, 67, 244, 0, 127, 226, 248, 162, 59, 47, 71, 54, 83, 62, 226, 95, 25, 138, 253, 76, 188, 233, 116, 161, 213, 175, 160, 56, 89, 224, 103, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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