Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11e7a7bd200897fd9f86e3ad8640ba9bb9143194fea7834779bc32696be22dd4

Tx prefix hash: dd0b11565bb10fd30f79491b018fbfb243cd64abed6b79c411f5ea9f8c8c6ae7
Tx public key: edc7db3d39621d01ee7cb13b6f2c769125760ec46eb94b685a0cdce31a8e7544
Timestamp: 1682782067 Timestamp [UCT]: 2023-04-29 15:27:47 Age [y:d:h:m:s]: 01:340:15:43:26
Block: 749250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504719 RingCT/type: yes/0
Extra: 01edc7db3d39621d01ee7cb13b6f2c769125760ec46eb94b685a0cdce31a8e7544021100000005b3164c24000000000000000000

1 output(s) for total of 2.020337504000 dcy

stealth address amount amount idx
00: 58b201c836f0184dcc7e19807fa5c7d1a6593c454a782fe96b5f094d9736edd4 2.020337504000 1197197 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": 749260, "vin": [ { "gen": { "height": 749250 } } ], "vout": [ { "amount": 2020337504, "target": { "key": "58b201c836f0184dcc7e19807fa5c7d1a6593c454a782fe96b5f094d9736edd4" } } ], "extra": [ 1, 237, 199, 219, 61, 57, 98, 29, 1, 238, 124, 177, 59, 111, 44, 118, 145, 37, 118, 14, 196, 110, 185, 75, 104, 90, 12, 220, 227, 26, 142, 117, 68, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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