Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bab081fb50bb5e583f739024ea0ba098f05e926bd1ae8b8e221d152adf40ad35

Tx prefix hash: 2cbbba8483d0d789ae03496fb1962eabaa090545209bbeb7fcf8b9d459df1c2f
Tx public key: 6102b16f18fcbb635a8d307ea435cead892fd34adca48cac4f15c35473e6e7d0
Timestamp: 1713347357 Timestamp [UCT]: 2024-04-17 09:49:17 Age [y:d:h:m:s]: 01:198:15:53:03
Block: 1002397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400636 RingCT/type: yes/0
Extra: 016102b16f18fcbb635a8d307ea435cead892fd34adca48cac4f15c35473e6e7d002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f614dc2410269a91110c570beb9f85019067a64e14264e1c648a1b5c8742e01 0.600000000000 1462913 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": 1002407, "vin": [ { "gen": { "height": 1002397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f614dc2410269a91110c570beb9f85019067a64e14264e1c648a1b5c8742e01" } } ], "extra": [ 1, 97, 2, 177, 111, 24, 252, 187, 99, 90, 141, 48, 126, 164, 53, 206, 173, 137, 47, 211, 74, 220, 164, 140, 172, 79, 21, 195, 84, 115, 230, 231, 208, 2, 17, 0, 0, 0, 5, 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