Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba9626a1b07d816a1a229002562b03d70c95db4913a29717f6e3f0fed76f010

Tx prefix hash: 3502686a455b87c77528ed81d02cdce689ef0a558c7bac52d05b3ea4b37926cb
Tx public key: 33c3d34678b818798207961cde1f6c6e15e1f9cc9cc813cfadf3beadf64b69ad
Timestamp: 1681615792 Timestamp [UCT]: 2023-04-16 03:29:52 Age [y:d:h:m:s]: 02:201:05:46:12
Block: 739567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 663690 RingCT/type: yes/0
Extra: 0133c3d34678b818798207961cde1f6c6e15e1f9cc9cc813cfadf3beadf64b69ad0211000000015029cbac000000000000000000

1 output(s) for total of 2.175242794000 dcy

stealth address amount amount idx
00: 95feefee4c732dd7c0ca5edacec96d156513bdb01b1e449aa85ddb64b2ab1a27 2.175242794000 1186424 of 0

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": 739577, "vin": [ { "gen": { "height": 739567 } } ], "vout": [ { "amount": 2175242794, "target": { "key": "95feefee4c732dd7c0ca5edacec96d156513bdb01b1e449aa85ddb64b2ab1a27" } } ], "extra": [ 1, 51, 195, 211, 70, 120, 184, 24, 121, 130, 7, 150, 28, 222, 31, 108, 110, 21, 225, 249, 204, 156, 200, 19, 207, 173, 243, 190, 173, 246, 75, 105, 173, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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