Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e64d03232d8dd04b78cce39773034df201528781f771ab4c770ea34c827ab0

Tx prefix hash: 770a6b6138241b417486fb0232bab3187d6b8b1f6ca2726f984a65b6790a9f9d
Tx public key: 4f0ad105f39efc9087fc877257100fd223b5232410a1ab7547861cdde98bfebf
Timestamp: 1696829156 Timestamp [UCT]: 2023-10-09 05:25:56 Age [y:d:h:m:s]: 01:251:06:05:35
Block: 865670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440538 RingCT/type: yes/0
Extra: 014f0ad105f39efc9087fc877257100fd223b5232410a1ab7547861cdde98bfebf02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.831143412000 dcy

stealth address amount amount idx
00: 1f83d3f20e3e4ba60c86bab5013673c21661f67c8d9d2aa795052b07a7ee1e56 0.831143412000 1320210 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": 865680, "vin": [ { "gen": { "height": 865670 } } ], "vout": [ { "amount": 831143412, "target": { "key": "1f83d3f20e3e4ba60c86bab5013673c21661f67c8d9d2aa795052b07a7ee1e56" } } ], "extra": [ 1, 79, 10, 209, 5, 243, 158, 252, 144, 135, 252, 135, 114, 87, 16, 15, 210, 35, 181, 35, 36, 16, 161, 171, 117, 71, 134, 28, 221, 233, 139, 254, 191, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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