Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e53ea9d310a7412821f99b389f397265cdad4c77f6b6a88c5968318173576a

Tx prefix hash: 6551714e16a8d80d38a03149d347ca2a682ff0bbd8302237f63c9bd23575b72e
Tx public key: 5056f5a594a7512fd0a71f4eb668f72263afc3dfce6845770e311d0a4fb64a01
Timestamp: 1719291891 Timestamp [UCT]: 2024-06-25 05:04:51 Age [y:d:h:m:s]: 00:324:19:43:44
Block: 1051672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232141 RingCT/type: yes/0
Extra: 015056f5a594a7512fd0a71f4eb668f72263afc3dfce6845770e311d0a4fb64a0102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5bafc500f619afe49cefdf12cc1a743901c71d15af44dd1ad2b15187ebcd7e1 0.600000000000 1521987 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": 1051682, "vin": [ { "gen": { "height": 1051672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5bafc500f619afe49cefdf12cc1a743901c71d15af44dd1ad2b15187ebcd7e1" } } ], "extra": [ 1, 80, 86, 245, 165, 148, 167, 81, 47, 208, 167, 31, 78, 182, 104, 247, 34, 99, 175, 195, 223, 206, 104, 69, 119, 14, 49, 29, 10, 79, 182, 74, 1, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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