Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aee935d01d0549726647083f7d73228f59fde451e71c98d18354fb21fc354c6

Tx prefix hash: 1f03a7a0e35fd0e170d178e4bc1f57c599f5745649f839fbfc222911394ed4f6
Tx public key: cfdbf7016f589f4c6256cc960a6dff0d48f27625806c258ef2f614da7095b294
Timestamp: 1703799563 Timestamp [UCT]: 2023-12-28 21:39:23 Age [y:d:h:m:s]: 01:138:09:13:02
Block: 923245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360045 RingCT/type: yes/0
Extra: 01cfdbf7016f589f4c6256cc960a6dff0d48f27625806c258ef2f614da7095b29402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d320f1ccdb27bcab43aa821e41b96f080008f4311b22356d23aa6ceab27eb769 0.600000000000 1380973 of 15

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": 923255, "vin": [ { "gen": { "height": 923245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d320f1ccdb27bcab43aa821e41b96f080008f4311b22356d23aa6ceab27eb769" } } ], "extra": [ 1, 207, 219, 247, 1, 111, 88, 159, 76, 98, 86, 204, 150, 10, 109, 255, 13, 72, 242, 118, 37, 128, 108, 37, 142, 242, 246, 20, 218, 112, 149, 178, 148, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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