Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf7145f58eb172e6581156b1bdf550dac86d73431dc849110601dcd6c7c52537

Tx prefix hash: 1f6928bffc76eebf82b4aa2cbed0b2fcc37ad4ecfc47e4f569fb99186c23a069
Tx public key: 540db10505e50201aa758b1a102cee9b532eef1e6a4d5b9e0a5344c6d6f867d9
Timestamp: 1717712111 Timestamp [UCT]: 2024-06-06 22:15:11 Age [y:d:h:m:s]: 00:283:14:23:59
Block: 1038590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202684 RingCT/type: yes/0
Extra: 01540db10505e50201aa758b1a102cee9b532eef1e6a4d5b9e0a5344c6d6f867d90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af2daab3af6691d440471c6794046364785eb95c1b83eb631a02a879fe6ee3fa 0.600000000000 1507151 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": 1038600, "vin": [ { "gen": { "height": 1038590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af2daab3af6691d440471c6794046364785eb95c1b83eb631a02a879fe6ee3fa" } } ], "extra": [ 1, 84, 13, 177, 5, 5, 229, 2, 1, 170, 117, 139, 26, 16, 44, 238, 155, 83, 46, 239, 30, 106, 77, 91, 158, 10, 83, 68, 198, 214, 248, 103, 217, 2, 17, 0, 0, 0, 3, 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