Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1572a41cc6163d551865aa4ac7a0ee5dbe049fc3dd3f05d7f06b3c2d3ab3f8d4

Tx prefix hash: 30c84e503c8db514203725c067d64fa7bdd0c171062e58881ca1bc107b076cc0
Tx public key: 1e22c80cb0058be0eb611322c384602f1b7f74e6ea87dae7c27cdd66e4fb25ed
Timestamp: 1719163605 Timestamp [UCT]: 2024-06-23 17:26:45 Age [y:d:h:m:s]: 00:293:05:50:06
Block: 1050605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209555 RingCT/type: yes/0
Extra: 011e22c80cb0058be0eb611322c384602f1b7f74e6ea87dae7c27cdd66e4fb25ed02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7accee6ed4d50fbf737f50aa8a039c728e852488ec76a1d7e4e94db7377da1a7 0.600000000000 1520780 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": 1050615, "vin": [ { "gen": { "height": 1050605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7accee6ed4d50fbf737f50aa8a039c728e852488ec76a1d7e4e94db7377da1a7" } } ], "extra": [ 1, 30, 34, 200, 12, 176, 5, 139, 224, 235, 97, 19, 34, 195, 132, 96, 47, 27, 127, 116, 230, 234, 135, 218, 231, 194, 124, 221, 102, 228, 251, 37, 237, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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