Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef053a180d990f428754d86b5f996e9a2c80d6ed64420aa30cb2339357924003

Tx prefix hash: 647f69e0e44e1db40b6d6caec638c61f26899300e42b9aca54595c1fef15042e
Tx public key: c5a1589d96bb52d063a2aa1e73fd3740beeba117ab1539c75d1116b14b13e647
Timestamp: 1577260439 Timestamp [UCT]: 2019-12-25 07:53:59 Age [y:d:h:m:s]: 05:043:22:02:49
Block: 31241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181200 RingCT/type: yes/0
Extra: 01c5a1589d96bb52d063a2aa1e73fd3740beeba117ab1539c75d1116b14b13e6470211000000024943cd9f000000000000000000

1 output(s) for total of 483.600185427000 dcy

stealth address amount amount idx
00: 12a9ba07be2020bdc0708c3b64bede1d96e40c4a9a81ad62ccd216f2f7d8818f 483.600185427000 51653 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": 31251, "vin": [ { "gen": { "height": 31241 } } ], "vout": [ { "amount": 483600185427, "target": { "key": "12a9ba07be2020bdc0708c3b64bede1d96e40c4a9a81ad62ccd216f2f7d8818f" } } ], "extra": [ 1, 197, 161, 88, 157, 150, 187, 82, 208, 99, 162, 170, 30, 115, 253, 55, 64, 190, 235, 161, 23, 171, 21, 57, 199, 93, 17, 22, 177, 75, 19, 230, 71, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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