Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e78638229dc4256347af12a3a2b56c555a6cca24356b106a8dd0cebe6ea9a2cc

Tx prefix hash: 5edf3a4624be18f610c755523dad66305c5b3a7409a8ba97cce0a7afe59ff7f2
Tx public key: b7da6f2f132e6641b42fd9a25e8e945c37cf3d4ff0abd284f56017eaa32e25ab
Timestamp: 1727909273 Timestamp [UCT]: 2024-10-02 22:47:53 Age [y:d:h:m:s]: 00:111:23:08:48
Block: 1123130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79995 RingCT/type: yes/0
Extra: 01b7da6f2f132e6641b42fd9a25e8e945c37cf3d4ff0abd284f56017eaa32e25ab021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee7a5ac5d8e4a3acc70d86cb984dcebbfd3bcf32106a2f11abeee3276ae7c66e 0.600000000000 1605663 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": 1123140, "vin": [ { "gen": { "height": 1123130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee7a5ac5d8e4a3acc70d86cb984dcebbfd3bcf32106a2f11abeee3276ae7c66e" } } ], "extra": [ 1, 183, 218, 111, 47, 19, 46, 102, 65, 180, 47, 217, 162, 94, 142, 148, 92, 55, 207, 61, 79, 240, 171, 210, 132, 245, 96, 23, 234, 163, 46, 37, 171, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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