Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484bfa730bb3ce4603aa5a76183f72226b291de5f53b59e7da3bfb1dbd44c71b

Tx prefix hash: d0cb3e3bd9cd90546f1215a1affe0d6a799c4f25c19f54daec19d0bb2f55b53b
Tx public key: e4e304b5243d717756f53ff23f3b08e6723f446d1518774790b36dfada9a98bb
Timestamp: 1707654284 Timestamp [UCT]: 2024-02-11 12:24:44 Age [y:d:h:m:s]: 01:049:06:39:40
Block: 955202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296257 RingCT/type: yes/0
Extra: 01e4e304b5243d717756f53ff23f3b08e6723f446d1518774790b36dfada9a98bb02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 236ec860435aee956ae645e8e7254b76e1c7046a7d47c5b44001fc1e0bf51be1 0.600000000000 1414488 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": 955212, "vin": [ { "gen": { "height": 955202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "236ec860435aee956ae645e8e7254b76e1c7046a7d47c5b44001fc1e0bf51be1" } } ], "extra": [ 1, 228, 227, 4, 181, 36, 61, 113, 119, 86, 245, 63, 242, 63, 59, 8, 230, 114, 63, 68, 109, 21, 24, 119, 71, 144, 179, 109, 250, 218, 154, 152, 187, 2, 17, 0, 0, 0, 3, 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