Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f63f039dd4b7a9d4ff0ef1ed2463c8e1d6695e6a93da4d39d16d595e8b4c158f

Tx prefix hash: e93b325d477a27ce9804795b830278c9f81dbb934ff0e57bec3f1daf7c1447cd
Tx public key: dca7f0b4fdceac2562c6d51e9ead156a3f7418b47bc17a42e1a2d50d2114eef8
Timestamp: 1711797778 Timestamp [UCT]: 2024-03-30 11:22:58 Age [y:d:h:m:s]: 01:055:06:10:50
Block: 989579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300466 RingCT/type: yes/0
Extra: 01dca7f0b4fdceac2562c6d51e9ead156a3f7418b47bc17a42e1a2d50d2114eef802110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91a448b9791dbba7f71fcfc8226a15d8b6d1a419f356cc6dd201ea3d4134e2f3 0.600000000000 1449878 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": 989589, "vin": [ { "gen": { "height": 989579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91a448b9791dbba7f71fcfc8226a15d8b6d1a419f356cc6dd201ea3d4134e2f3" } } ], "extra": [ 1, 220, 167, 240, 180, 253, 206, 172, 37, 98, 198, 213, 30, 158, 173, 21, 106, 63, 116, 24, 180, 123, 193, 122, 66, 225, 162, 213, 13, 33, 20, 238, 248, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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