Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1c288432cddda282479c20b27b6c8ee9adfcb6b38aa9344bc5c347c5b9e0996

Tx prefix hash: f38f8cb2d13265bc1a9279bae2333f0a862eeb5a6ccb9aeb689b33bb01b915ae
Tx public key: aa8003f1d9c78b8e73f9533d343fd50d028e5e3282110a6bfe02c4aa477c303b
Timestamp: 1705154029 Timestamp [UCT]: 2024-01-13 13:53:49 Age [y:d:h:m:s]: 01:310:20:13:23
Block: 934460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480995 RingCT/type: yes/0
Extra: 01aa8003f1d9c78b8e73f9533d343fd50d028e5e3282110a6bfe02c4aa477c303b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7771ff9a94beecc622246ccbccc07720e414d89eba21f5b74ad97d22f15cd8f4 0.600000000000 1392470 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": 934470, "vin": [ { "gen": { "height": 934460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7771ff9a94beecc622246ccbccc07720e414d89eba21f5b74ad97d22f15cd8f4" } } ], "extra": [ 1, 170, 128, 3, 241, 217, 199, 139, 142, 115, 249, 83, 61, 52, 63, 213, 13, 2, 142, 94, 50, 130, 17, 10, 107, 254, 2, 196, 170, 71, 124, 48, 59, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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