Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b7a3e8c963a8756e7550200e67bf2411c50ed9ef38c912193f9a321d4047dc

Tx prefix hash: d01ef1e3de11509e858fef90090fabcd54a4c9bd5747a35f8babfc5e4bfa5e9b
Tx public key: 6b9873dfb48e34b1fe2d453e7391b7930e5e82ec834e2a99881732aadbaecea8
Timestamp: 1743592275 Timestamp [UCT]: 2025-04-02 11:11:15 Age [y:d:h:m:s]: 00:076:22:00:20
Block: 1252656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54895 RingCT/type: yes/0
Extra: 016b9873dfb48e34b1fe2d453e7391b7930e5e82ec834e2a99881732aadbaecea8021100000003a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4350db1613e332b5ef3cecfde4e1d1ad3bb0a374b9e64ca4ce50d7fb8e844af1 0.600000000000 1739737 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": 1252666, "vin": [ { "gen": { "height": 1252656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4350db1613e332b5ef3cecfde4e1d1ad3bb0a374b9e64ca4ce50d7fb8e844af1" } } ], "extra": [ 1, 107, 152, 115, 223, 180, 142, 52, 177, 254, 45, 69, 62, 115, 145, 183, 147, 14, 94, 130, 236, 131, 78, 42, 153, 136, 23, 50, 170, 219, 174, 206, 168, 2, 17, 0, 0, 0, 3, 162, 237, 1, 107, 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