Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d57dacbdbd2ead813bbc39b09ff9b1e00c69f8f27fe705f051f4ad18567f79

Tx prefix hash: b261ccef13b3de9d89cea0538050d315d9582e3d1ca4b13d34866d01e3778715
Tx public key: bebae0565f1a2f8bdb4d33b117650f94b8f49af3c29edd3ec625aed8de58bfe1
Timestamp: 1711367240 Timestamp [UCT]: 2024-03-25 11:47:20 Age [y:d:h:m:s]: 01:083:06:47:17
Block: 986010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320414 RingCT/type: yes/0
Extra: 01bebae0565f1a2f8bdb4d33b117650f94b8f49af3c29edd3ec625aed8de58bfe10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df794a9f38ac68507266c5ef97eaaa7124c151694de30d8cd4cda8b4826f663 0.600000000000 1446235 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": 986020, "vin": [ { "gen": { "height": 986010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df794a9f38ac68507266c5ef97eaaa7124c151694de30d8cd4cda8b4826f663" } } ], "extra": [ 1, 190, 186, 224, 86, 95, 26, 47, 139, 219, 77, 51, 177, 23, 101, 15, 148, 184, 244, 154, 243, 194, 158, 221, 62, 198, 37, 174, 216, 222, 88, 191, 225, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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