Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4901499379aa1e24b4388b90b6843d45afe48896cafbf096d02c963dd59cbbb5

Tx prefix hash: d2d39ed52794d03239fb3630b29da5631d360d777bca273faebd518628e404b7
Tx public key: 640be5656ab6171338c3cb95a1add5948244c64d2713f2b4d2088a3e63d4dba8
Timestamp: 1583078283 Timestamp [UCT]: 2020-03-01 15:58:03 Age [y:d:h:m:s]: 04:318:06:30:38
Block: 74537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121495 RingCT/type: yes/0
Extra: 01640be5656ab6171338c3cb95a1add5948244c64d2713f2b4d2088a3e63d4dba802110000003c724f989b000000000000000000

1 output(s) for total of 347.565179006000 dcy

stealth address amount amount idx
00: db5e030d1d061798c566c79fbb11c0dcccd0ad18bee88769d900cef869cf43de 347.565179006000 137925 of 0

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": 74547, "vin": [ { "gen": { "height": 74537 } } ], "vout": [ { "amount": 347565179006, "target": { "key": "db5e030d1d061798c566c79fbb11c0dcccd0ad18bee88769d900cef869cf43de" } } ], "extra": [ 1, 100, 11, 229, 101, 106, 182, 23, 19, 56, 195, 203, 149, 161, 173, 213, 148, 130, 68, 198, 77, 39, 19, 242, 180, 210, 8, 138, 62, 99, 212, 219, 168, 2, 17, 0, 0, 0, 60, 114, 79, 152, 155, 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