Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d035f1343eb5f4c3c383e2857a96bf1faea7f3e05756905a0ddc3ea071df477

Tx prefix hash: a8fac016a5b891b0a75356634ecbb24f669131394ebf4dacdb32f87708a19a6e
Tx public key: 8fbe4c887a61d9dedd571148d00d0ae8aa54411365fbc8206141b0ad8679237e
Timestamp: 1713440739 Timestamp [UCT]: 2024-04-18 11:45:39 Age [y:d:h:m:s]: 00:312:18:46:57
Block: 1003162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223584 RingCT/type: yes/0
Extra: 018fbe4c887a61d9dedd571148d00d0ae8aa54411365fbc8206141b0ad8679237e02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c496a093e3204b3ea0f1d164d56158f5a1373cb7b3cbe3bfd8012ee2c25a3a8 0.600000000000 1463692 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": 1003172, "vin": [ { "gen": { "height": 1003162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c496a093e3204b3ea0f1d164d56158f5a1373cb7b3cbe3bfd8012ee2c25a3a8" } } ], "extra": [ 1, 143, 190, 76, 136, 122, 97, 217, 222, 221, 87, 17, 72, 208, 13, 10, 232, 170, 84, 65, 19, 101, 251, 200, 32, 97, 65, 176, 173, 134, 121, 35, 126, 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