Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4fe50bdf3e8202c8915b25fdccf56beed41a007f8f63816a770ecd733ef5f8b

Tx prefix hash: 705d822b11abc4b0f1e97bdd910707ac1e63cb3cfa445b272a54523278c825f1
Tx public key: c32a7774482bb5f3d95154a84832b55dacac407713650e9b83e966b770f327c3
Timestamp: 1699786284 Timestamp [UCT]: 2023-11-12 10:51:24 Age [y:d:h:m:s]: 01:213:03:06:52
Block: 889974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413515 RingCT/type: yes/0
Extra: 01c32a7774482bb5f3d95154a84832b55dacac407713650e9b83e966b770f327c302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.690472983000 dcy

stealth address amount amount idx
00: 1b6dad8779c7825149aa6bbee42e521853b76b98848e90786b50464a41c53986 0.690472983000 1345993 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": 889984, "vin": [ { "gen": { "height": 889974 } } ], "vout": [ { "amount": 690472983, "target": { "key": "1b6dad8779c7825149aa6bbee42e521853b76b98848e90786b50464a41c53986" } } ], "extra": [ 1, 195, 42, 119, 116, 72, 43, 181, 243, 217, 81, 84, 168, 72, 50, 181, 93, 172, 172, 64, 119, 19, 101, 14, 155, 131, 233, 102, 183, 112, 243, 39, 195, 2, 17, 0, 0, 0, 1, 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