Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e64ed099a6c0cf7c0f9f490f75933eca831887b06a4a22f3a001f9b947ad8bd

Tx prefix hash: dd0856edbc471255063bf328e5b9a5b5aa603d632885f2714649b11a90227d04
Tx public key: 67a3273dac952b719b18e5b1a2957157b20ed2ba181180651b2c44e26e0fb37f
Timestamp: 1577987148 Timestamp [UCT]: 2020-01-02 17:45:48 Age [y:d:h:m:s]: 05:039:00:20:25
Block: 37353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177608 RingCT/type: yes/0
Extra: 0167a3273dac952b719b18e5b1a2957157b20ed2ba181180651b2c44e26e0fb37f0211000000314ac5aa02000000000000000000

1 output(s) for total of 461.567112042000 dcy

stealth address amount amount idx
00: 5f5d77fac5b0342234b8e6acf9567fddf05e971e6550fd3c87a38c6a742791c7 461.567112042000 63379 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": 37363, "vin": [ { "gen": { "height": 37353 } } ], "vout": [ { "amount": 461567112042, "target": { "key": "5f5d77fac5b0342234b8e6acf9567fddf05e971e6550fd3c87a38c6a742791c7" } } ], "extra": [ 1, 103, 163, 39, 61, 172, 149, 43, 113, 155, 24, 229, 177, 162, 149, 113, 87, 178, 14, 210, 186, 24, 17, 128, 101, 27, 44, 68, 226, 110, 15, 179, 127, 2, 17, 0, 0, 0, 49, 74, 197, 170, 2, 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