Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a385a08511e3c718b3692f3be64caaa10c7dfceb57dd68e34a2fc2d948419db5

Tx prefix hash: 4e175185ad23fdbb9a9a8a33c4a4554f49a4a3ba0e55453d78b9f821d8401ad2
Tx public key: d5c64ca7c072d84c12f824d4171b9c82f451a46be96cfbe7fcacc274d4b61b78
Timestamp: 1732825222 Timestamp [UCT]: 2024-11-28 20:20:22 Age [y:d:h:m:s]: 00:167:12:16:51
Block: 1163785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119555 RingCT/type: yes/0
Extra: 01d5c64ca7c072d84c12f824d4171b9c82f451a46be96cfbe7fcacc274d4b61b780211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48e9b311ee3147cab8db74e1f0a123604d8feeb6455c9e912bde579d446f85e5 0.600000000000 1649454 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": 1163795, "vin": [ { "gen": { "height": 1163785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48e9b311ee3147cab8db74e1f0a123604d8feeb6455c9e912bde579d446f85e5" } } ], "extra": [ 1, 213, 198, 76, 167, 192, 114, 216, 76, 18, 248, 36, 212, 23, 27, 156, 130, 244, 81, 164, 107, 233, 108, 251, 231, 252, 172, 194, 116, 212, 182, 27, 120, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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