Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab1fd43cc3ed55c0e7907c07c8ba7be6e4b61f07038411c3938a04a71594dd7e

Tx prefix hash: c22b6306256a0d57184dd31dc51b59e1a32a933ac477ccb9bd452f2ab8023b16
Tx public key: 848d3a3c4c4cc301ddbde66343d1b095148f5dbf92dc0114a6624ac88c23440b
Timestamp: 1700612377 Timestamp [UCT]: 2023-11-22 00:19:37 Age [y:d:h:m:s]: 01:062:22:42:58
Block: 896828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306337 RingCT/type: yes/0
Extra: 01848d3a3c4c4cc301ddbde66343d1b095148f5dbf92dc0114a6624ac88c23440b0211000000024b8f5122000000000000000000

1 output(s) for total of 0.655294515000 dcy

stealth address amount amount idx
00: d4f164d8705a6e2b5b32e6bd0a8c4d08b6aef9bf7cdf96dbb048d4dc23748bc6 0.655294515000 1353171 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": 896838, "vin": [ { "gen": { "height": 896828 } } ], "vout": [ { "amount": 655294515, "target": { "key": "d4f164d8705a6e2b5b32e6bd0a8c4d08b6aef9bf7cdf96dbb048d4dc23748bc6" } } ], "extra": [ 1, 132, 141, 58, 60, 76, 76, 195, 1, 221, 189, 230, 99, 67, 209, 176, 149, 20, 143, 93, 191, 146, 220, 1, 20, 166, 98, 74, 200, 140, 35, 68, 11, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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