Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d8d0f7c3c8999fe7268d006fb6a0e7c4087ca970774529fc500a1ffbda5ceaa

Tx prefix hash: 3dab8c4867285c7c23f62d09fa0b1a86027b6ba9e2dc07b3804a26eedb8f7f4d
Tx public key: f105615331a92467807f0d86aed7168b43617c24aa40aff4fc410a860f513085
Timestamp: 1730320179 Timestamp [UCT]: 2024-10-30 20:29:39 Age [y:d:h:m:s]: 00:069:20:54:18
Block: 1143044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49983 RingCT/type: yes/0
Extra: 01f105615331a92467807f0d86aed7168b43617c24aa40aff4fc410a860f51308502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 230c3dcb1dec55bbbca0446c2c01fbf1e85f789ffb61383c291ac72a28e9dd40 0.600000000000 1626901 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": 1143054, "vin": [ { "gen": { "height": 1143044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "230c3dcb1dec55bbbca0446c2c01fbf1e85f789ffb61383c291ac72a28e9dd40" } } ], "extra": [ 1, 241, 5, 97, 83, 49, 169, 36, 103, 128, 127, 13, 134, 174, 215, 22, 139, 67, 97, 124, 36, 170, 64, 175, 244, 252, 65, 10, 134, 15, 81, 48, 133, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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