Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f2213ae00d3a956b0e7c877d2eb873aeb5c90912a846a0b14e4bb04baab12d

Tx prefix hash: 3b6000edb5a70fdd5dea5132d46679691fc9235ea7520afe38e53f8c5ee4362d
Tx public key: 62bcb3a765e837082617bf184041aa2eedab8ae5a5314fae9535ce3433a0b5b6
Timestamp: 1729878189 Timestamp [UCT]: 2024-10-25 17:43:09 Age [y:d:h:m:s]: 00:154:06:59:16
Block: 1139412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110068 RingCT/type: yes/0
Extra: 0162bcb3a765e837082617bf184041aa2eedab8ae5a5314fae9535ce3433a0b5b6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c305f47eaf21605fe4b52b7a22f69f3020c11bcc5ca1cdffdb7f180f31fa7dde 0.600000000000 1623199 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": 1139422, "vin": [ { "gen": { "height": 1139412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c305f47eaf21605fe4b52b7a22f69f3020c11bcc5ca1cdffdb7f180f31fa7dde" } } ], "extra": [ 1, 98, 188, 179, 167, 101, 232, 55, 8, 38, 23, 191, 24, 64, 65, 170, 46, 237, 171, 138, 229, 165, 49, 79, 174, 149, 53, 206, 52, 51, 160, 181, 182, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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