Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d1f4c565d002b75062bed4a9463ee33af9bb62a1c895f7574df99311d8e7cb1

Tx prefix hash: 0b3b5eca8c35f51f7088cfed8959709d16cc89d759507f1274aaa9b3f7fe56fb
Tx public key: d18cdb14100f14ec71d1937f2ec0fdec98305d4066b9449b85a5a998862cf5a6
Timestamp: 1700892787 Timestamp [UCT]: 2023-11-25 06:13:07 Age [y:d:h:m:s]: 01:178:17:57:29
Block: 899143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388962 RingCT/type: yes/0
Extra: 01d18cdb14100f14ec71d1937f2ec0fdec98305d4066b9449b85a5a998862cf5a6021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.643822238000 dcy

stealth address amount amount idx
00: f84b71dcdcc7b7c7d16a2522ecb52c540cbfbec8f15bd927fd68573d35eb2973 0.643822238000 1355586 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": 899153, "vin": [ { "gen": { "height": 899143 } } ], "vout": [ { "amount": 643822238, "target": { "key": "f84b71dcdcc7b7c7d16a2522ecb52c540cbfbec8f15bd927fd68573d35eb2973" } } ], "extra": [ 1, 209, 140, 219, 20, 16, 15, 20, 236, 113, 209, 147, 127, 46, 192, 253, 236, 152, 48, 93, 64, 102, 185, 68, 155, 133, 165, 169, 152, 134, 44, 245, 166, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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