Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d2802fc9a6055ce019cef9bb135ed921f7f198f9073fbecf05eb86b64a2e7e3

Tx prefix hash: 8154d8ddc59b1d62f14d42b02caadc4616d2b82662af5b696d46fda7db1e3489
Tx public key: 2f654693f99fc0902d07f50b69c9cb21abc45d6112682b1e0435f8dee1240746
Timestamp: 1703667904 Timestamp [UCT]: 2023-12-27 09:05:04 Age [y:d:h:m:s]: 01:023:03:00:40
Block: 922155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277860 RingCT/type: yes/0
Extra: 012f654693f99fc0902d07f50b69c9cb21abc45d6112682b1e0435f8dee124074602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cb9b7a369eb7ce9707e53a691bb6978d72ba2f44db96d5dfeed53e3d2e25630 0.600000000000 1379849 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": 922165, "vin": [ { "gen": { "height": 922155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cb9b7a369eb7ce9707e53a691bb6978d72ba2f44db96d5dfeed53e3d2e25630" } } ], "extra": [ 1, 47, 101, 70, 147, 249, 159, 192, 144, 45, 7, 245, 11, 105, 201, 203, 33, 171, 196, 93, 97, 18, 104, 43, 30, 4, 53, 248, 222, 225, 36, 7, 70, 2, 17, 0, 0, 0, 1, 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