Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed1e3912f6c815f603c34a1eb83de917df99e71f1d40bef460c756b0aace14f3

Tx prefix hash: 75fc6ba79fc260a0f69f6b8d5099d717c6057a56d5859d8163b24af8fc608e37
Tx public key: e96e759f4b8444c07dc5e2c07074024ce339c3a00366329ec2495d5dc4f38117
Timestamp: 1724115911 Timestamp [UCT]: 2024-08-20 01:05:11 Age [y:d:h:m:s]: 00:251:21:35:35
Block: 1091687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179914 RingCT/type: yes/0
Extra: 01e96e759f4b8444c07dc5e2c07074024ce339c3a00366329ec2495d5dc4f3811702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16eeaca79ac33b64289825dc0d199a2b90168db8ce2fb054317b6c1ccab58aa0 0.600000000000 1566320 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": 1091697, "vin": [ { "gen": { "height": 1091687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16eeaca79ac33b64289825dc0d199a2b90168db8ce2fb054317b6c1ccab58aa0" } } ], "extra": [ 1, 233, 110, 117, 159, 75, 132, 68, 192, 125, 197, 226, 192, 112, 116, 2, 76, 227, 57, 195, 160, 3, 102, 50, 158, 194, 73, 93, 93, 196, 243, 129, 23, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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