Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de02af7348e8345c08026e0f47305d5af4ede26ea68fe95d2782ee53954a3493

Tx prefix hash: b773a0c74fa21d7b9eae33245cd4986dd33be5c37b01f598b681fcb04193bf48
Tx public key: ff6832a4d8fb8cb2ca9e03b8fa75323152cfb9cd7ffc6eddbdf734c09c86533c
Timestamp: 1717833873 Timestamp [UCT]: 2024-06-08 08:04:33 Age [y:d:h:m:s]: 00:364:23:10:36
Block: 1039607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260864 RingCT/type: yes/0
Extra: 01ff6832a4d8fb8cb2ca9e03b8fa75323152cfb9cd7ffc6eddbdf734c09c86533c02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6bfa9f692e60d3e6fbcdbc298e0d5be03b2398404ecf358c35651b0656f896 0.600000000000 1508250 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": 1039617, "vin": [ { "gen": { "height": 1039607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6bfa9f692e60d3e6fbcdbc298e0d5be03b2398404ecf358c35651b0656f896" } } ], "extra": [ 1, 255, 104, 50, 164, 216, 251, 140, 178, 202, 158, 3, 184, 250, 117, 50, 49, 82, 207, 185, 205, 127, 252, 110, 221, 189, 247, 52, 192, 156, 134, 83, 60, 2, 17, 0, 0, 0, 10, 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