Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cf0c47119f161799104fa3fed3214f5c3351626dd7ede0ce4c65cb651af0550

Tx prefix hash: b0d7cdaec98fa052d95e8a5b0b4f7e31797d7c330351b2da13e4c1f64902067d
Tx public key: b7a6184a400b9de095eea2ee39c2750d7c82c0b538db7b1ed6fd9fff6677954e
Timestamp: 1746836452 Timestamp [UCT]: 2025-05-10 00:20:52 Age [y:d:h:m:s]: 00:211:14:51:33
Block: 1279513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148968 RingCT/type: yes/0
Extra: 01b7a6184a400b9de095eea2ee39c2750d7c82c0b538db7b1ed6fd9fff6677954e0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9e85eb72223b871efbf4ac457092cfadf4b07f56732fc60397cf1829284a14b 0.600000000000 1766890 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": 1279523, "vin": [ { "gen": { "height": 1279513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9e85eb72223b871efbf4ac457092cfadf4b07f56732fc60397cf1829284a14b" } } ], "extra": [ 1, 183, 166, 24, 74, 64, 11, 157, 224, 149, 238, 162, 238, 57, 194, 117, 13, 124, 130, 192, 181, 56, 219, 123, 30, 214, 253, 159, 255, 102, 119, 149, 78, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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