Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd5f7caf64dcbc16b9c7f058c734db0fd23f36c3fe4a81f58ac8acd83bea6399

Tx prefix hash: 8162a95cdff3cfaf8db75edbfd1886c2083bde63842959ddac04ca71737fb3d8
Tx public key: 24071dd244a0aa82188202130c9a1ab0b506c66c243b099ce62beaeef0a4999a
Timestamp: 1705867761 Timestamp [UCT]: 2024-01-21 20:09:21 Age [y:d:h:m:s]: 01:035:09:22:19
Block: 940363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286358 RingCT/type: yes/0
Extra: 0124071dd244a0aa82188202130c9a1ab0b506c66c243b099ce62beaeef0a4999a02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f363ed4c5a24486cbe78ce2c183dc681dbc23d1204a36ece58c8405d2f88ffe 0.600000000000 1398499 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": 940373, "vin": [ { "gen": { "height": 940363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f363ed4c5a24486cbe78ce2c183dc681dbc23d1204a36ece58c8405d2f88ffe" } } ], "extra": [ 1, 36, 7, 29, 210, 68, 160, 170, 130, 24, 130, 2, 19, 12, 154, 26, 176, 181, 6, 198, 108, 36, 59, 9, 156, 230, 43, 234, 238, 240, 164, 153, 154, 2, 17, 0, 0, 0, 9, 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