Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495ef36b180b267f04dc744c714e2c16b8aa0c338c942cc1d15ff23eb20711ac

Tx prefix hash: c16047c8663c0de8b1044b9bead760ee6bcfad2ea3f1e95abc5305eaa3cdccb9
Tx public key: eb1c3c25fd3876a683b1c83b2e202b329de436942199153f698dc52795b3ef0e
Timestamp: 1728481924 Timestamp [UCT]: 2024-10-09 13:52:04 Age [y:d:h:m:s]: 00:046:05:27:53
Block: 1127870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33021 RingCT/type: yes/0
Extra: 01eb1c3c25fd3876a683b1c83b2e202b329de436942199153f698dc52795b3ef0e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bd4a63becd12e45d670e9ecc2fb90f7064eafd4bba060473f21d1399e130229 0.600000000000 1610683 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": 1127880, "vin": [ { "gen": { "height": 1127870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bd4a63becd12e45d670e9ecc2fb90f7064eafd4bba060473f21d1399e130229" } } ], "extra": [ 1, 235, 28, 60, 37, 253, 56, 118, 166, 131, 177, 200, 59, 46, 32, 43, 50, 157, 228, 54, 148, 33, 153, 21, 63, 105, 141, 197, 39, 149, 179, 239, 14, 2, 17, 0, 0, 0, 6, 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