Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 406492b353cfc502be6c47b28aec9bee70b9538726bb86089ccc3e7292af2fb2

Tx prefix hash: 24be8567cd26fa1c26d01efeaefe61c558f76a2747d79b5cb7ce84c4fc5ce0b2
Tx public key: a8c03e752922c1b96ea0ac7e37e4e6363ac8c0ea33a90cdbc17ff296fead7223
Timestamp: 1576424732 Timestamp [UCT]: 2019-12-15 15:45:32 Age [y:d:h:m:s]: 04:346:08:43:55
Block: 27487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133558 RingCT/type: yes/0
Extra: 01a8c03e752922c1b96ea0ac7e37e4e6363ac8c0ea33a90cdbc17ff296fead7223021100000015ad433a0b000000000000000000

1 output(s) for total of 497.651164406000 dcy

stealth address amount amount idx
00: 52363281320557a7233606577ed201cdb7c8c7cc7b700d439e87e549012eb66e 497.651164406000 45489 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": 27497, "vin": [ { "gen": { "height": 27487 } } ], "vout": [ { "amount": 497651164406, "target": { "key": "52363281320557a7233606577ed201cdb7c8c7cc7b700d439e87e549012eb66e" } } ], "extra": [ 1, 168, 192, 62, 117, 41, 34, 193, 185, 110, 160, 172, 126, 55, 228, 230, 54, 58, 200, 192, 234, 51, 169, 12, 219, 193, 127, 242, 150, 254, 173, 114, 35, 2, 17, 0, 0, 0, 21, 173, 67, 58, 11, 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