Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbd21bb3dba90e1e29ef67ace3ec08c3c6975bcb92829cb97c3083444b927881

Tx prefix hash: 536f89421c32f51905c9ed3f648013c6ee27f87b77aa61d0a5f744922e66ab4b
Tx public key: f7ad2ccb95c1afcf1425719068a6ca49b3442b4bd3dba040d378093c4a7f097e
Timestamp: 1716005736 Timestamp [UCT]: 2024-05-18 04:15:36 Age [y:d:h:m:s]: 00:325:14:09:18
Block: 1024442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232713 RingCT/type: yes/0
Extra: 01f7ad2ccb95c1afcf1425719068a6ca49b3442b4bd3dba040d378093c4a7f097e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1922606f9aab7778dfd83d134b7b882fc2137e36bc611a7d77a83b611b075de 0.600000000000 1490195 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": 1024452, "vin": [ { "gen": { "height": 1024442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1922606f9aab7778dfd83d134b7b882fc2137e36bc611a7d77a83b611b075de" } } ], "extra": [ 1, 247, 173, 44, 203, 149, 193, 175, 207, 20, 37, 113, 144, 104, 166, 202, 73, 179, 68, 43, 75, 211, 219, 160, 64, 211, 120, 9, 60, 74, 127, 9, 126, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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