Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec7d2ec7f27a2374e4cb01a6af9d2232555712481116c4cc1b2b4d9fcb30fc93

Tx prefix hash: 41188290aa0ca71cb60b311f107d8f2a95d5e32da7a804e9dfc0119336de1ac4
Tx public key: ec4057db62b7a957f6aa277b70b5b7fbb536ec8db205d9d502f0861c81daa572
Timestamp: 1699388941 Timestamp [UCT]: 2023-11-07 20:29:01 Age [y:d:h:m:s]: 01:149:17:00:44
Block: 886680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368183 RingCT/type: yes/0
Extra: 01ec4057db62b7a957f6aa277b70b5b7fbb536ec8db205d9d502f0861c81daa57202110000000675e3f0e9000000000000000000

1 output(s) for total of 0.708045366000 dcy

stealth address amount amount idx
00: 3eb9c8962fd80e0d1625e74c792561dc4c0adf8d3ecb8ae986f52ce1d8de4e31 0.708045366000 1342513 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": 886690, "vin": [ { "gen": { "height": 886680 } } ], "vout": [ { "amount": 708045366, "target": { "key": "3eb9c8962fd80e0d1625e74c792561dc4c0adf8d3ecb8ae986f52ce1d8de4e31" } } ], "extra": [ 1, 236, 64, 87, 219, 98, 183, 169, 87, 246, 170, 39, 123, 112, 181, 183, 251, 181, 54, 236, 141, 178, 5, 217, 213, 2, 240, 134, 28, 129, 218, 165, 114, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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