Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03b197891f306a0b4c108eeb699db9085d746531ec7ff66c9edc3b0f1cd69769

Tx prefix hash: fdc0ae12a09fc2faf7f69ccc49094e5ddfeff5e324b71be3614925e5bff08298
Tx public key: 1d47943069b0b8c91a3e4527a872405e1a4b1d64e791bab849aa12b5568a5157
Timestamp: 1713824810 Timestamp [UCT]: 2024-04-22 22:26:50 Age [y:d:h:m:s]: 00:151:18:31:08
Block: 1006359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108709 RingCT/type: yes/0
Extra: 011d47943069b0b8c91a3e4527a872405e1a4b1d64e791bab849aa12b5568a515702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c256249c3a27ff32ffc370ca15f4bf15cd9aaa9fcb4182326614616cb7f91c6 0.600000000000 1467373 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": 1006369, "vin": [ { "gen": { "height": 1006359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c256249c3a27ff32ffc370ca15f4bf15cd9aaa9fcb4182326614616cb7f91c6" } } ], "extra": [ 1, 29, 71, 148, 48, 105, 176, 184, 201, 26, 62, 69, 39, 168, 114, 64, 94, 26, 75, 29, 100, 231, 145, 186, 184, 73, 170, 18, 181, 86, 138, 81, 87, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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