Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 347f574790a390f0ec71c83e94c338cc28a87be883eaddcd65a3f46e21359b7a

Tx prefix hash: 6d51e12968677caa9fdce78d986698baa5b188b98b5398395bab6b7442ef94ab
Tx public key: 6ab003b36cece0b40b12a0119c3e0de5272a67a020d7c9e83c366aa2f55f76b2
Timestamp: 1750349276 Timestamp [UCT]: 2025-06-19 16:07:56 Age [y:d:h:m:s]: 00:147:18:38:26
Block: 1308471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103422 RingCT/type: yes/0
Extra: 016ab003b36cece0b40b12a0119c3e0de5272a67a020d7c9e83c366aa2f55f76b2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f844c2c7e8e908acaefbd40dbd9d96a76e70785430fad070f3af2b4aa1f7dfb 0.600000000000 1796084 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": 1308481, "vin": [ { "gen": { "height": 1308471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f844c2c7e8e908acaefbd40dbd9d96a76e70785430fad070f3af2b4aa1f7dfb" } } ], "extra": [ 1, 106, 176, 3, 179, 108, 236, 224, 180, 11, 18, 160, 17, 156, 62, 13, 229, 39, 42, 103, 160, 32, 215, 201, 232, 60, 54, 106, 162, 245, 95, 118, 178, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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