Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20f5e6a141835f6dd8ddb4dd8e9178559eb42e9f59cdcc8f9d962e885a431cee

Tx prefix hash: a27e5edda0ec1808845de5368a31771a82e6ad738e041547f1cec78f11d02c76
Tx public key: 19f225d58632b79c47035e113ae92fd590871c3b3c01f5271f75eadecf4455e4
Timestamp: 1699408746 Timestamp [UCT]: 2023-11-08 01:59:06 Age [y:d:h:m:s]: 01:147:11:22:29
Block: 886848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366588 RingCT/type: yes/0
Extra: 0119f225d58632b79c47035e113ae92fd590871c3b3c01f5271f75eadecf4455e402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.707138415000 dcy

stealth address amount amount idx
00: 55ed4ef72313665b8e5cd958939aaa24f3f782e52ec1a006c69572ebe03f9ded 0.707138415000 1342695 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": 886858, "vin": [ { "gen": { "height": 886848 } } ], "vout": [ { "amount": 707138415, "target": { "key": "55ed4ef72313665b8e5cd958939aaa24f3f782e52ec1a006c69572ebe03f9ded" } } ], "extra": [ 1, 25, 242, 37, 213, 134, 50, 183, 156, 71, 3, 94, 17, 58, 233, 47, 213, 144, 135, 28, 59, 60, 1, 245, 39, 31, 117, 234, 222, 207, 68, 85, 228, 2, 17, 0, 0, 0, 5, 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