Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43691e644e9b7dabe5af0e3b01718c259c839615b1620710fb28cae295d5808f

Tx prefix hash: 70a3bd7bbe9e36ce25982eb9f017dbfcc6e14b6e1805ab52c6125d1b6413102e
Tx public key: bac34bd4509b10f781c108ba0678ffd4ec08f125ce035f96e8329482c2ee251c
Timestamp: 1724054871 Timestamp [UCT]: 2024-08-19 08:07:51 Age [y:d:h:m:s]: 00:241:15:05:25
Block: 1091180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172550 RingCT/type: yes/0
Extra: 01bac34bd4509b10f781c108ba0678ffd4ec08f125ce035f96e8329482c2ee251c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b98f5d55fa5bb27fbda362b45606f33da0aecd50edcc5b4b1b1b582f4a88551 0.600000000000 1565809 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": 1091190, "vin": [ { "gen": { "height": 1091180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b98f5d55fa5bb27fbda362b45606f33da0aecd50edcc5b4b1b1b582f4a88551" } } ], "extra": [ 1, 186, 195, 75, 212, 80, 155, 16, 247, 129, 193, 8, 186, 6, 120, 255, 212, 236, 8, 241, 37, 206, 3, 95, 150, 232, 50, 148, 130, 194, 238, 37, 28, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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