Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dfa923bfb2d5e1d76e7a57d30f768fa9b97493ccedf2846974de30aabcdbc6e

Tx prefix hash: 9d1242756fceed356e3a57c4f62f9548d9fee005896546a88756d07fe8a7a92b
Tx public key: 571f387f2b1bcf9feda327227605d88463aba2201cd7f5e38c848d7d2d1a9d82
Timestamp: 1757500907 Timestamp [UCT]: 2025-09-10 10:41:47 Age [y:d:h:m:s]: 00:104:01:08:46
Block: 1365369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74465 RingCT/type: yes/0
Extra: 01571f387f2b1bcf9feda327227605d88463aba2201cd7f5e38c848d7d2d1a9d82021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd1187bd2b8615a9197cbf5d573097b9e925663df6d9daf23e3ea4e5a64286fe 0.600000000000 1853408 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": 1365379, "vin": [ { "gen": { "height": 1365369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd1187bd2b8615a9197cbf5d573097b9e925663df6d9daf23e3ea4e5a64286fe" } } ], "extra": [ 1, 87, 31, 56, 127, 43, 27, 207, 159, 237, 163, 39, 34, 118, 5, 216, 132, 99, 171, 162, 32, 28, 215, 245, 227, 140, 132, 141, 125, 45, 26, 157, 130, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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