Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4572544d432ee9cbcbe1cff1820e5dee745b3b30b52e9f35f9ce12770affe27c

Tx prefix hash: 16bd006ae1046436725a9fb22cad7c822039bc36aeeb515a29bba47e08263c8b
Tx public key: c0728a719a8938b6cec2598abed8f8e640f7a5e59bcedc2ff57e16f612b99883
Timestamp: 1732856881 Timestamp [UCT]: 2024-11-29 05:08:01 Age [y:d:h:m:s]: 00:115:19:17:31
Block: 1164050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82557 RingCT/type: yes/0
Extra: 01c0728a719a8938b6cec2598abed8f8e640f7a5e59bcedc2ff57e16f612b998830211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a121fc1e65021d6df6f0f2987b06b528b008e5997685e79e4c28d5c6241b594f 0.600000000000 1649721 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": 1164060, "vin": [ { "gen": { "height": 1164050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a121fc1e65021d6df6f0f2987b06b528b008e5997685e79e4c28d5c6241b594f" } } ], "extra": [ 1, 192, 114, 138, 113, 154, 137, 56, 182, 206, 194, 89, 138, 190, 216, 248, 230, 64, 247, 165, 229, 155, 206, 220, 47, 245, 126, 22, 246, 18, 185, 152, 131, 2, 17, 0, 0, 0, 2, 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