Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb45127d751d0cbf2c3cd96a332227d5975e86ee5bc7a5f82c9bda0df1a84458

Tx prefix hash: da5e91706adcae6de3e140b44631e7f43b81a811ef44a770e3677a699c7dcacd
Tx public key: c51ff8bfacf764fe42a5ab0162f25906811011e18cfdc0ac1b8309201e49f29d
Timestamp: 1726430373 Timestamp [UCT]: 2024-09-15 19:59:33 Age [y:d:h:m:s]: 00:114:10:34:00
Block: 1110864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81838 RingCT/type: yes/0
Extra: 01c51ff8bfacf764fe42a5ab0162f25906811011e18cfdc0ac1b8309201e49f29d021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6734c616f8708b10e820e302b40b9ae9ca8d2e728a1c6746d5d6f28673393aa0 0.600000000000 1589625 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": 1110874, "vin": [ { "gen": { "height": 1110864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6734c616f8708b10e820e302b40b9ae9ca8d2e728a1c6746d5d6f28673393aa0" } } ], "extra": [ 1, 197, 31, 248, 191, 172, 247, 100, 254, 66, 165, 171, 1, 98, 242, 89, 6, 129, 16, 17, 225, 140, 253, 192, 172, 27, 131, 9, 32, 30, 73, 242, 157, 2, 17, 0, 0, 0, 9, 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