Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1316aaf239d34895997d97def73e09a6b5e4bffcfc46731467f11bea6002f640

Tx prefix hash: 734a53672f70d94e405ff6227475063f5f348a5102dcf038443c494d6c1c6a92
Tx public key: ea2fc1a71c0fe987b7d49c11beaf67efb56d957c0e4bb77cf8b139a9797c0e3f
Timestamp: 1761357334 Timestamp [UCT]: 2025-10-25 01:55:34 Age [y:d:h:m:s]: 00:011:12:13:47
Block: 1397322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8213 RingCT/type: yes/0
Extra: 01ea2fc1a71c0fe987b7d49c11beaf67efb56d957c0e4bb77cf8b139a9797c0e3f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07a48a7d06884ac817a685f43a7b150fe60f68bedd2d558dfe8477b08d84c506 0.600000000000 1885613 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": 1397332, "vin": [ { "gen": { "height": 1397322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07a48a7d06884ac817a685f43a7b150fe60f68bedd2d558dfe8477b08d84c506" } } ], "extra": [ 1, 234, 47, 193, 167, 28, 15, 233, 135, 183, 212, 156, 17, 190, 175, 103, 239, 181, 109, 149, 124, 14, 75, 183, 124, 248, 177, 57, 169, 121, 124, 14, 63, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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