Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2a2e89e18a9359d2ad406438d6c1bf85153f0949ee74226186846687d4a4d4c

Tx prefix hash: dac2f9bea4b0115f22b6775cf16f0e67479a63ea3303ab73a4ae8fb109ae0315
Tx public key: bf6d3897c82bfd029c75f4d2754b38939b909336d11f5a61208db4e497251868
Timestamp: 1738114534 Timestamp [UCT]: 2025-01-29 01:35:34 Age [y:d:h:m:s]: 00:139:02:53:50
Block: 1207318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99388 RingCT/type: yes/0
Extra: 01bf6d3897c82bfd029c75f4d2754b38939b909336d11f5a61208db4e4972518680211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d102e33f5a05b533e586b795cb62e543b48b70284eaa38ca799b4a693f3f5a9 0.600000000000 1694041 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": 1207328, "vin": [ { "gen": { "height": 1207318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d102e33f5a05b533e586b795cb62e543b48b70284eaa38ca799b4a693f3f5a9" } } ], "extra": [ 1, 191, 109, 56, 151, 200, 43, 253, 2, 156, 117, 244, 210, 117, 75, 56, 147, 155, 144, 147, 54, 209, 31, 90, 97, 32, 141, 180, 228, 151, 37, 24, 104, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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