Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 746db549931e24515e8c20ba4b304bce6fdbd8f121c1e80b7196bc3a53eb3d4c

Tx prefix hash: 98cdeb368e4656957adf04e50947c49a9ab928426ff64653d98f553edb076594
Tx public key: 0c87b85e846daccc9a9dd39ad743e7f06fdcf67b317d0a13a3ab9b5fa1aa1e55
Timestamp: 1719431922 Timestamp [UCT]: 2024-06-26 19:58:42 Age [y:d:h:m:s]: 00:263:15:13:44
Block: 1052840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188394 RingCT/type: yes/0
Extra: 010c87b85e846daccc9a9dd39ad743e7f06fdcf67b317d0a13a3ab9b5fa1aa1e5502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34750fc5d8dc692104a5b1ccf4ddd6bebba8e96e48c2f7a362552e2aef7ead9e 0.600000000000 1523173 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": 1052850, "vin": [ { "gen": { "height": 1052840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34750fc5d8dc692104a5b1ccf4ddd6bebba8e96e48c2f7a362552e2aef7ead9e" } } ], "extra": [ 1, 12, 135, 184, 94, 132, 109, 172, 204, 154, 157, 211, 154, 215, 67, 231, 240, 111, 220, 246, 123, 49, 125, 10, 19, 163, 171, 155, 95, 161, 170, 30, 85, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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