Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac4ffc0c18b04f18efa63540538db1d33cf26553123af5d45c055f1c279205e0

Tx prefix hash: 8fa7d0cafb33633ba74dad5f7ecbe16390f36030c9b46df1a72587574995b221
Tx public key: 5e50502711b2081c8d97de1d15b38b7a3fb9ac921cf894a6af241f02daaa5e48
Timestamp: 1731481347 Timestamp [UCT]: 2024-11-13 07:02:27 Age [y:d:h:m:s]: 00:215:06:00:45
Block: 1152640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153611 RingCT/type: yes/0
Extra: 015e50502711b2081c8d97de1d15b38b7a3fb9ac921cf894a6af241f02daaa5e48021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b8c842336ad2e43bcfa6cabbc47349699503aec43a63fde202fae457ea4492f 0.600000000000 1638243 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": 1152650, "vin": [ { "gen": { "height": 1152640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b8c842336ad2e43bcfa6cabbc47349699503aec43a63fde202fae457ea4492f" } } ], "extra": [ 1, 94, 80, 80, 39, 17, 178, 8, 28, 141, 151, 222, 29, 21, 179, 139, 122, 63, 185, 172, 146, 28, 248, 148, 166, 175, 36, 31, 2, 218, 170, 94, 72, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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