Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8137313ee128a1b00dc9648e022d288b82dad80685f69375bcbfca44c37d6572

Tx prefix hash: 8d288f1f9ace425e0a1f6573c2a983194847cbe83e40401ce8629f2183bb1d14
Tx public key: 419a286c8ea617baef3192b518d1611d6cea2fd16f3f31554478f21cad976324
Timestamp: 1696823292 Timestamp [UCT]: 2023-10-09 03:48:12 Age [y:d:h:m:s]: 02:032:02:02:57
Block: 865617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542549 RingCT/type: yes/0
Extra: 01419a286c8ea617baef3192b518d1611d6cea2fd16f3f31554478f21cad97632402110000000b4b8f5122000000000000000000

1 output(s) for total of 0.831479561000 dcy

stealth address amount amount idx
00: 6c599776b144d4d5956c2b22fd015d28fc3443bb45a7f2ec43bccb1b1077fef3 0.831479561000 1320155 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": 865627, "vin": [ { "gen": { "height": 865617 } } ], "vout": [ { "amount": 831479561, "target": { "key": "6c599776b144d4d5956c2b22fd015d28fc3443bb45a7f2ec43bccb1b1077fef3" } } ], "extra": [ 1, 65, 154, 40, 108, 142, 166, 23, 186, 239, 49, 146, 181, 24, 209, 97, 29, 108, 234, 47, 209, 111, 63, 49, 85, 68, 120, 242, 28, 173, 151, 99, 36, 2, 17, 0, 0, 0, 11, 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