Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11bab270c887d092c701193efce627a42a1a86cb123007ad4422ac7ad0f088a6

Tx prefix hash: 986a2a00180d1bcfa5f329b34cc106efbc8deba07f6f3d5087fdced2f3dbbf20
Tx public key: 632da55a88063c48aa5725ccaba969d48b85d73f9b5fc9a267d1aa14b58b31ab
Timestamp: 1711432705 Timestamp [UCT]: 2024-03-26 05:58:25 Age [y:d:h:m:s]: 01:084:18:37:03
Block: 986545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321463 RingCT/type: yes/0
Extra: 01632da55a88063c48aa5725ccaba969d48b85d73f9b5fc9a267d1aa14b58b31ab0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7b57b1b03e5495a1d69902d5b073b0680c348dc155a87d4b6a3a438a55ac87e 0.600000000000 1446774 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": 986555, "vin": [ { "gen": { "height": 986545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7b57b1b03e5495a1d69902d5b073b0680c348dc155a87d4b6a3a438a55ac87e" } } ], "extra": [ 1, 99, 45, 165, 90, 136, 6, 60, 72, 170, 87, 37, 204, 171, 169, 105, 212, 139, 133, 215, 63, 155, 95, 201, 162, 103, 209, 170, 20, 181, 139, 49, 171, 2, 17, 0, 0, 0, 4, 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