Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e2c4cb0698f954001104f5a0940e2487a8e652d6c0285d0620b4c37adf7a40

Tx prefix hash: d6c223361c826e10d01478b3470d4ecf106faf3e67d9317d826acb966506726f
Tx public key: d17eba7f141275ab1fb13ec573504562bcfacb62acafe9753b58a2f5aaa08cf0
Timestamp: 1718589798 Timestamp [UCT]: 2024-06-17 02:03:18 Age [y:d:h:m:s]: 00:220:21:17:30
Block: 1045876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158011 RingCT/type: yes/0
Extra: 01d17eba7f141275ab1fb13ec573504562bcfacb62acafe9753b58a2f5aaa08cf00211000000013690c78b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f827e3bdaec58f335d5b7c081e65a343969740ff7fd2effbdcff3c4d9bc5aae3 0.600000000000 1515573 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": 1045886, "vin": [ { "gen": { "height": 1045876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f827e3bdaec58f335d5b7c081e65a343969740ff7fd2effbdcff3c4d9bc5aae3" } } ], "extra": [ 1, 209, 126, 186, 127, 20, 18, 117, 171, 31, 177, 62, 197, 115, 80, 69, 98, 188, 250, 203, 98, 172, 175, 233, 117, 59, 88, 162, 245, 170, 160, 140, 240, 2, 17, 0, 0, 0, 1, 54, 144, 199, 139, 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