Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42a5fe5b925a1b5b195d0986473fa6478c6fba3d823052009754b1ac7588dc9f

Tx prefix hash: 79c271483eecb55df5e7fece16d9a09c9c7982949d284e05804f96a79f216a2f
Tx public key: 4a09dc11e5c9f6dd5254fdb642ac04eb7bd0675565cabe8c4d074cedbb4c46e0
Timestamp: 1703303235 Timestamp [UCT]: 2023-12-23 03:47:15 Age [y:d:h:m:s]: 01:331:23:08:48
Block: 919123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496114 RingCT/type: yes/0
Extra: 014a09dc11e5c9f6dd5254fdb642ac04eb7bd0675565cabe8c4d074cedbb4c46e002110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da0a275ffcf98cf64b7cac7d20ed2025b2531c08bc21b3ecf39d4d266f39aee6 0.600000000000 1376787 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": 919133, "vin": [ { "gen": { "height": 919123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da0a275ffcf98cf64b7cac7d20ed2025b2531c08bc21b3ecf39d4d266f39aee6" } } ], "extra": [ 1, 74, 9, 220, 17, 229, 201, 246, 221, 82, 84, 253, 182, 66, 172, 4, 235, 123, 208, 103, 85, 101, 202, 190, 140, 77, 7, 76, 237, 187, 76, 70, 224, 2, 17, 0, 0, 0, 4, 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