Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c0b71de846308c8dd5dca63837bf783cfbfb9ca165454d2f43222bcad9efe75

Tx prefix hash: b4fb299f442156ef799d2442ab818f5b03aec15221aa94a8bb0445477e3a6e88
Tx public key: d896fa1f5faf18dd603cda45f9e691aff48ce324c392f76fb1eb56f92672de9a
Timestamp: 1714681388 Timestamp [UCT]: 2024-05-02 20:23:08 Age [y:d:h:m:s]: 00:297:14:11:27
Block: 1013464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212698 RingCT/type: yes/0
Extra: 01d896fa1f5faf18dd603cda45f9e691aff48ce324c392f76fb1eb56f92672de9a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c640a65e0f4e6db903310fd321c4b110df08e70e3b8719d153cf8a39e9e3d22b 0.600000000000 1476287 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": 1013474, "vin": [ { "gen": { "height": 1013464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c640a65e0f4e6db903310fd321c4b110df08e70e3b8719d153cf8a39e9e3d22b" } } ], "extra": [ 1, 216, 150, 250, 31, 95, 175, 24, 221, 96, 60, 218, 69, 249, 230, 145, 175, 244, 140, 227, 36, 195, 146, 247, 111, 177, 235, 86, 249, 38, 114, 222, 154, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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