Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bbe9f57d158801f514a7b60e51bd0b5d185a25e94276a68321e90ef86272aa1

Tx prefix hash: 52bb7741a377f1e86c503982b383d4273199d7ab983ff48c40d0bb73af447340
Tx public key: 1a1464bbf0ee4adf80eebc530471a9ab83b9a316062e6bc387e12aa45ac6fcce
Timestamp: 1738149915 Timestamp [UCT]: 2025-01-29 11:25:15 Age [y:d:h:m:s]: 00:322:00:16:55
Block: 1207605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227939 RingCT/type: yes/0
Extra: 011a1464bbf0ee4adf80eebc530471a9ab83b9a316062e6bc387e12aa45ac6fcce0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0232d4a019be06fd8fe82f4e2c17faacba351e7d0123d5b03b6d63a47b2ab556 0.600000000000 1694330 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": 1207615, "vin": [ { "gen": { "height": 1207605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0232d4a019be06fd8fe82f4e2c17faacba351e7d0123d5b03b6d63a47b2ab556" } } ], "extra": [ 1, 26, 20, 100, 187, 240, 238, 74, 223, 128, 238, 188, 83, 4, 113, 169, 171, 131, 185, 163, 22, 6, 46, 107, 195, 135, 225, 42, 164, 90, 198, 252, 206, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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