Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec9750cbb17063a2d6e5117813f095ab6df8644e36790e76e2a3dde4729e0ab9

Tx prefix hash: bd55e3c56cb503ffda50c83b6c920b64df3846ee490aab3dcc42100de135c0cb
Tx public key: fa9a07c9f3d94caa561f43ba8a0660b580ba3c283630562b27e36b47109b1dd6
Timestamp: 1715636061 Timestamp [UCT]: 2024-05-13 21:34:21 Age [y:d:h:m:s]: 00:350:10:21:12
Block: 1021368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250516 RingCT/type: yes/0
Extra: 01fa9a07c9f3d94caa561f43ba8a0660b580ba3c283630562b27e36b47109b1dd60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eb3d763b75fe15ce650a777ee93c6c2f83245fe68f49eb10bf4c87fa6d0ca5c 0.600000000000 1485673 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": 1021378, "vin": [ { "gen": { "height": 1021368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eb3d763b75fe15ce650a777ee93c6c2f83245fe68f49eb10bf4c87fa6d0ca5c" } } ], "extra": [ 1, 250, 154, 7, 201, 243, 217, 76, 170, 86, 31, 67, 186, 138, 6, 96, 181, 128, 186, 60, 40, 54, 48, 86, 43, 39, 227, 107, 71, 16, 155, 29, 214, 2, 17, 0, 0, 0, 1, 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