Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a7df8fb675a188a5e95f4c8dedc86406d3eeb0ca088b64abb967c45dc54505e

Tx prefix hash: e3444bf4eea1d19fffde199e665d07b397b144ef38dca1fd8b19e574017ebaf7
Tx public key: 9f14ea8d9bc0eb63ccc2ab78666f7c361ade9a58136d6516a228a22213dcbbc9
Timestamp: 1673239114 Timestamp [UCT]: 2023-01-09 04:38:34 Age [y:d:h:m:s]: 02:070:21:33:20
Block: 670739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572374 RingCT/type: yes/0
Extra: 019f14ea8d9bc0eb63ccc2ab78666f7c361ade9a58136d6516a228a22213dcbbc9021100000001faf35c9c000000000000000000

1 output(s) for total of 3.677589173000 dcy

stealth address amount amount idx
00: 78ba766bdf530e8c8643502e849cc837ba4505f4c6e081a2e406834f1f2adfd4 3.677589173000 1112154 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": 670749, "vin": [ { "gen": { "height": 670739 } } ], "vout": [ { "amount": 3677589173, "target": { "key": "78ba766bdf530e8c8643502e849cc837ba4505f4c6e081a2e406834f1f2adfd4" } } ], "extra": [ 1, 159, 20, 234, 141, 155, 192, 235, 99, 204, 194, 171, 120, 102, 111, 124, 54, 26, 222, 154, 88, 19, 109, 101, 22, 162, 40, 162, 34, 19, 220, 187, 201, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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