Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18c90de1c5381baaa812b851ff00fa094f5622b26122ebbc1be4be325b581f37

Tx prefix hash: 847f4a8679c1f8e958c7fdc578c298905e4555fc7dcaf67671fb3f0218d6ef56
Tx public key: 66d1391066c97a8dc4ca0f6d9bfbfef0a749b06cd350c0f6dea6ddba6f4764a7
Timestamp: 1577950211 Timestamp [UCT]: 2020-01-02 07:30:11 Age [y:d:h:m:s]: 05:306:16:34:49
Block: 37017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366675 RingCT/type: yes/0
Extra: 0166d1391066c97a8dc4ca0f6d9bfbfef0a749b06cd350c0f6dea6ddba6f4764a70211000000308a2ee0d9000000000000000000

1 output(s) for total of 462.751850912000 dcy

stealth address amount amount idx
00: 4da7c05ca67ccf580a0e2e9098f8d1bc6b8c129801939896d063f22230bea1b5 462.751850912000 62771 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": 37027, "vin": [ { "gen": { "height": 37017 } } ], "vout": [ { "amount": 462751850912, "target": { "key": "4da7c05ca67ccf580a0e2e9098f8d1bc6b8c129801939896d063f22230bea1b5" } } ], "extra": [ 1, 102, 209, 57, 16, 102, 201, 122, 141, 196, 202, 15, 109, 155, 251, 254, 240, 167, 73, 176, 108, 211, 80, 192, 246, 222, 166, 221, 186, 111, 71, 100, 167, 2, 17, 0, 0, 0, 48, 138, 46, 224, 217, 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