Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e924048062c2e10c737eaeaef89ce5694cc4f8524ebd9f2e1744e33e98b850

Tx prefix hash: 3ada4bf4dc4922f72b9fe340b593f4a15ca35af03aca915543ea954fc8e1d13a
Tx public key: 8524c10f5aac931fb9f4d530bb54801a20dcfde983e3c02be63d83ab59561e50
Timestamp: 1757068677 Timestamp [UCT]: 2025-09-05 10:37:57 Age [y:d:h:m:s]: 00:124:01:31:00
Block: 1361844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88762 RingCT/type: yes/0
Extra: 018524c10f5aac931fb9f4d530bb54801a20dcfde983e3c02be63d83ab59561e50021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 812a0649835cdc291a32aac5cfe8f993fdf08146489c9f45c5e8f3c000231260 0.600000000000 1849867 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": 1361854, "vin": [ { "gen": { "height": 1361844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "812a0649835cdc291a32aac5cfe8f993fdf08146489c9f45c5e8f3c000231260" } } ], "extra": [ 1, 133, 36, 193, 15, 90, 172, 147, 31, 185, 244, 213, 48, 187, 84, 128, 26, 32, 220, 253, 233, 131, 227, 192, 43, 230, 61, 131, 171, 89, 86, 30, 80, 2, 17, 0, 0, 0, 5, 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