Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ef7b8fdb59ff9361fa2c22bf20c43ce502a65ebac2b64bfbc80c179691a569

Tx prefix hash: 553c9f8cc8d6605cbaea0cccb3e6e78c0f4d8c15093e16d0bd0f8138e03c1b10
Tx public key: 04f57758a146939ca6cb9776ba506a449878d30b014013bfbd3141237cb4a82e
Timestamp: 1711734505 Timestamp [UCT]: 2024-03-29 17:48:25 Age [y:d:h:m:s]: 01:046:07:33:18
Block: 989049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294072 RingCT/type: yes/0
Extra: 0104f57758a146939ca6cb9776ba506a449878d30b014013bfbd3141237cb4a82e02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0de5bad30dd176f63e5aeb7bbb6e0cac8ebfc0a88c283c07c52289040b33d53e 0.600000000000 1449344 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": 989059, "vin": [ { "gen": { "height": 989049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0de5bad30dd176f63e5aeb7bbb6e0cac8ebfc0a88c283c07c52289040b33d53e" } } ], "extra": [ 1, 4, 245, 119, 88, 161, 70, 147, 156, 166, 203, 151, 118, 186, 80, 106, 68, 152, 120, 211, 11, 1, 64, 19, 191, 189, 49, 65, 35, 124, 180, 168, 46, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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