Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6586ccdc566d2e4ba5de845dc4ba092d041938e6a64d04ae14cb980039d7fd57

Tx prefix hash: c8bcdc919518e228087e3e30bd7e8f1dc10d4c561070497d274f85e4bb4db034
Tx public key: 367786e1b18496ad5309df41a04b270146f719274bd4f99ef1d037774d7fc9a9
Timestamp: 1723792638 Timestamp [UCT]: 2024-08-16 07:17:18 Age [y:d:h:m:s]: 00:234:16:52:25
Block: 1088995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167606 RingCT/type: yes/0
Extra: 01367786e1b18496ad5309df41a04b270146f719274bd4f99ef1d037774d7fc9a9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c7f72a8caf87f8e589dd6b959ad1adb407b5327c4fe26cccfc4894ab10aa52e 0.600000000000 1563614 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": 1089005, "vin": [ { "gen": { "height": 1088995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c7f72a8caf87f8e589dd6b959ad1adb407b5327c4fe26cccfc4894ab10aa52e" } } ], "extra": [ 1, 54, 119, 134, 225, 177, 132, 150, 173, 83, 9, 223, 65, 160, 75, 39, 1, 70, 247, 25, 39, 75, 212, 249, 158, 241, 208, 55, 119, 77, 127, 201, 169, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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