Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f33375694458e7da35eb9f957c37fe84127a6609a837efa58775b523f51d5cd

Tx prefix hash: b73af485a5ac1a6478169b9a9f4193505eda0b67aa35dd6011f060741384e607
Tx public key: adc4b90c8d336d41d68a18e908babfa388c499c9a0854904dcea28cc6a61e25b
Timestamp: 1736955959 Timestamp [UCT]: 2025-01-15 15:45:59 Age [y:d:h:m:s]: 00:153:15:50:49
Block: 1197973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109532 RingCT/type: yes/0
Extra: 01adc4b90c8d336d41d68a18e908babfa388c499c9a0854904dcea28cc6a61e25b02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb6c49d59047c6f7d3c45ccb0c06e36f19f4541754af4e2c26f1a97af0d0fde8 0.600000000000 1684590 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": 1197983, "vin": [ { "gen": { "height": 1197973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb6c49d59047c6f7d3c45ccb0c06e36f19f4541754af4e2c26f1a97af0d0fde8" } } ], "extra": [ 1, 173, 196, 185, 12, 141, 51, 109, 65, 214, 138, 24, 233, 8, 186, 191, 163, 136, 196, 153, 201, 160, 133, 73, 4, 220, 234, 40, 204, 106, 97, 226, 91, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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