Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8b06b9e1fdfab0cab9ee8a69f91f64511eacd3a763add380f4f457ef76d443

Tx prefix hash: 82e74b453ce23b2b8b5590771e14630d5242899d21a892ffcb5dbe20fd9c8455
Tx public key: d63da421fd75904141ce48b1706947f931708070672d0f6e68ed8b99874736ec
Timestamp: 1583854977 Timestamp [UCT]: 2020-03-10 15:42:57 Age [y:d:h:m:s]: 04:291:15:29:56
Block: 79872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103560 RingCT/type: yes/0
Extra: 01d63da421fd75904141ce48b1706947f931708070672d0f6e68ed8b99874736ec021100000008203e3db0000000000000000000

1 output(s) for total of 333.702305453000 dcy

stealth address amount amount idx
00: 643e0e8097807d45eac013c289ecc07c99a1d0e8d69687ab2cbaae1d71c78d25 333.702305453000 146150 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": 79882, "vin": [ { "gen": { "height": 79872 } } ], "vout": [ { "amount": 333702305453, "target": { "key": "643e0e8097807d45eac013c289ecc07c99a1d0e8d69687ab2cbaae1d71c78d25" } } ], "extra": [ 1, 214, 61, 164, 33, 253, 117, 144, 65, 65, 206, 72, 177, 112, 105, 71, 249, 49, 112, 128, 112, 103, 45, 15, 110, 104, 237, 139, 153, 135, 71, 54, 236, 2, 17, 0, 0, 0, 8, 32, 62, 61, 176, 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